-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix test issue where warning was being raised but not captured #151
Conversation
e00c1d5
to
0468bc0
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #151 +/- ##
==========================================
+ Coverage 90.23% 90.36% +0.13%
==========================================
Files 5 5
Lines 635 654 +19
==========================================
+ Hits 573 591 +18
- Misses 62 63 +1 ☔ View full report in Codecov by Sentry. |
3562143
to
af9ffb0
Compare
So adding try finally block seemed to surface a part of the issue, it looks as if the expected error is being clobbered by a
|
2d2e479
to
f91b351
Compare
So if you look at the test output the warning is raised but
pytest.warn
doesn't seem to capture it but recwarn does?